Batch Troubleshooting

This help topic will provide insight into some of the more common problems that may arise when using batches in netFORUM.

Payment Uses a Credit from an Unclosed Batch

This usually means that the invoice was paid with a credit but the system will not let you close the batch without first closing the batch where the credit resides.

Fix:

  1. Run the exception.
  2. Go to that invoice and from that you can see the customer. If you look at that customer’s credits, you can find the batch that the credit is in.
  3. Close that batch.
  4. Once you close that batch, you should be able to close the original batch.

Posting a Batch and Nothing Happens?

You close a batch without any problems but when you attempt to post the batch, the screen just refreshes, does not execute the posting but no errors are displayed.

The Issue - There is an export file with the same name already in the tempfiles/iweb/temp directory. It does a JavaScript windows confirmation message box asking if you want to delete the existing file. With Ajax running on this form you will not see this message box and therefore can't respond to the confirmation that you wish to overwrite the existing file with your new export file so it does nothing.

Fix:

One workaround is to go into user preferences and temporary disable the EnableAjax user option setting. Run the batch close process and then re-set preferences again. Also if one has folder access they could delete this export file from the temp folder and then post the batch again.

Fiscal Period

If the batch has financial information related to a membership that is not covered by the Accounting Periods (effective to expire) then you will be unable to close the batch. Make sure to cover the total span of the membership's life.

Batch date must fall within the period

Batch Dates must fall between the Accounting Period of the batch or else you will get an error when saving.

Batch name with YYYY-MM-DD-WEB

We recommend that you do not create batches with this naming convention. Web batches are created automatically based on this naming format, and various business rules rely on web batches being named in this format, for example, suppose the following batches are automatically created:

  • 2013-04-28-WEB-001
  • 2013-04-28-WEB-002

If you manually create a batch with the following name, errors will result:

  • 2013-04-28-WEB-01